This beta contains many behind-the-scenes changes designed to better unify our code between different platform versions of SkyDemon. It also contains many minor changes and improvements, and support for GAFOR area forecasts in Germany.

Please feel free to test this on your Android devices (it's available from our beta page) and report back here how you get on.

Thanks!

Tim

great work as ever, some remarks concerning the GAFOR area forecast. There are some time related inconsistences. The german GAFOR areas are depicted by an outline in matching colors - these ones are correct and up to date. A tap inside one of these areas gives a correct reading of GAFOR condition & actual time. The matching 3x2 hours time scale display seems to be wrong and outdated, in my case the first one of the day from 03:00Z to 09:00Z even at 17:00Z.. Additionally the yellow frame & little dot displaying the valid time segment/progess is missing with the german areas & the alpine routes as well.

thx & keep up the excellent work

-mike

Hi Tim,

thanks for this new German GAFOR feature, which I was waiting for since I moved away from 'Flightplanner/Skymap' to Skydemon.
Due to its Beta status I suppose that there are still not all planned features being realized in the current 3.6.6.31382 version.
But nevertheless some remarks and suggestions from my side:

- the color coding used to indicate the general status in the original DWD maps is (closed(X)=red, marginal(M)=orange, difficult(D)=Yellow, open(O)=green, clear(C)=blue). When looking at the Skydemon map I can see many 'difficult' areas outlined in green (I have not checked all the forecast zones). It might be good practice to have the color coding accordingly to the one used by DWD.

- when zoomed in deep enough, these little 3 boxes appear, which obviously should represent the 3 forecast timeframes and the according color codes. These are also not correct. For instance there is a blue middel square displayed between two green ones for the ED32 zone while the official DWD forecast has only D and M (yellow and orange) forecasted for the same timeframes.

- currently only the general staus like D, M, O etc. is used. It might be good to have the full code inlcuding the number (like M2, D4 etc.), because the number gives important additional information about visibility and ceiling. These should be shown within the boxes on the map and also when opening the detailled information window.

- when zooming out to more then 2m the GAFOR areas disappear from the map. So it is not possible to get a general picture about the wheather situation for a larger area without scrolling thru the map at a lower zoom range. So when planning a route over a grater distance you need to scroll along the routing to get a complete GAFOR wheather status.

So - that is it for the moment ;-)
Nevertheless I want to thank You and all your Coworkers a lot for this really great job that you are doing - especially for your customers here in Germany! Thank You!

-berndHS

Hi Tim,

Could you please check the two following scenario in the new beta version as SD is crashing in this two circumstances:
FLARM input
1. $PFLAA is missing <AcftType> -> crash
2. non-directional targets ->crash; found out that SD needs in $PFLAA the <GroundSpeed> as 0.0, should not be the case for non-directional targets / FLARM 7.0, This field is empty if stealth mode is activated either on the target or own aircraft and for non-directional targets.

SD 3.6.6.31382
Android 5.1.1

Serge

Small point: flight details tab has black line through middle of red and yellow cautions.
Nexus 7(2013) 6.0.1
Regards
Pete

Update: lines not apparent on Nexus 7 (2012)

Thanks all for the feedback. We have corrected the GAFOR timecode selection for the public release which will happen later today. No German-proprietary GAFOR information is included at the moment, we will review whether (and how) to include this in the future when the feature has had a chance to settle in.

Serge, this thread really isn't the best place to discuss your implementation of the Flarm protocol.

Still getting lines with latest release
.....and the ability to delete aircraft profiles from app and cloud seems to have disappeared 

The Delete button absence is a bug, will be fixed later today. Unfortunately it wasn't picked up in either internal or external beta testing.

Without seeing a screenshot of the "lines" to which you refer, unfortunately we can't really see what you are referring to Pete.

Bug wasn't apparent on the beta's I tried.
A screenshot as requested.
Regards
Pete